Skip to content

jspecify and java update#10

Open
SirCotare wants to merge 13 commits into
mainfrom
enforce_jspecify
Open

jspecify and java update#10
SirCotare wants to merge 13 commits into
mainfrom
enforce_jspecify

Conversation

@SirCotare
Copy link
Copy Markdown
Member

@SirCotare SirCotare commented May 15, 2026

target: 2.0.0 (final)

known: readme is still out dated. won't fix now. this is built for our gradle integration

with usage example here: https://github.com/aboutbits/finstral-composer-api/pull/676

@SirCotare SirCotare self-assigned this May 15, 2026
@SirCotare

This comment has been minimized.

SirCotare

This comment was marked as resolved.

@ThoSap
Copy link
Copy Markdown
Member

ThoSap commented May 15, 2026

I would release 2.0.0 once we migrated this lib to use Gradle + Axion Release Plugin like https://github.com/aboutbits/postgresql-operator/blob/main/build.gradle.kts#L11-L29 does.

Also the readme.md needs some care.

@SirCotare SirCotare requested a review from ThoSap May 15, 2026 13:48
@SirCotare
Copy link
Copy Markdown
Member Author

I would release 2.0.0 once we migrated this lib to use Gradle + Axion Release Plugin like aboutbits/postgresql-operator@main/build.gradle.kts#L11-L29 does.

Also the readme.md needs some care.

ok.. so we stay on RC for now. just take a look it you think this and the usage are OK the way they are now

Copy link
Copy Markdown
Member

@ThoSap ThoSap left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't remember if our Checkstyle config allows this, but I would name all it.aboutbits.checkstyle.Jspecify* classes JSpecify.

Otherwise LGTM 👍🏼

Comment thread pom.xml
<java.version>25</java.version>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
<checkstyle.version>13.4.2</checkstyle.version>
<junit.version>6.0.3</junit.version>
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

https://docs.junit.org/6.1.0/release-notes.html

Suggested change
<junit.version>6.0.3</junit.version>
<junit.version>6.1.0</junit.version>

Comment thread pom.xml
<checkstyle.version>13.4.2</checkstyle.version>
<junit.version>6.0.3</junit.version>
<errorprone.version>2.49.0</errorprone.version>
<nullaway.version>0.13.2</nullaway.version>
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
<nullaway.version>0.13.2</nullaway.version>
<nullaway.version>0.13.4</nullaway.version>

Comment on lines +8 to +9
import static org.junit.jupiter.api.Assertions.assertEquals;
import static org.junit.jupiter.api.Assertions.assertTrue;
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've seen multiple files using the JUnit assertions instead of AssertJ.
The AssertJ lib is not yet included in the pom.xml.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will not work in our main project as with the DbMessageSource by default we can't use params, except when we specially handle it in the CustomGlobalExceptionHandler.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nevermind, in the test ArchitectureTest test context Spring Boot is not present (I think), so MessageSource is not relevant here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants